October 22nd, 2001, 10:49 AM
Setting up subnets
Hi there, this is an extention of a topic I posted in the Apache forum but got asked to move it here. I have several virtual hosts set up, all of them working fine. My main domain is www.actconsult.net with several subnets pointing to out IIS server (intranet. demo. and test.) These all work fine.
I also want to set up some subnets that actually reside on the server and have thus set up virtual a host for sql.actconsult.net.
I was unable to find any documentation to help me so first I set up a new zone - obviously that's wrong.
ScriptAlias /cgi-bin/ /home/sites/sql/cgi-bin/
CustomLog /home/sites/sql/logs/access.log combined
I have now have this in the nameD file for actconsult.net:
This all works fine except for the sql.actconsult.net bit.
actconsult 43200 IN SOA dns1.actconsult.net. hostmaster.actconsult.net. (
2001102202 3600 900 1209600 43200 )
43200 IN NS dns1.actconsult.net.
43200 IN NS dns2.actconsult.net.
43200 IN MX 5 mx1.actconsult.net.
43200 IN MX 10 mx2.actconsult.net.
ns1 43200 IN A 184.108.40.206
dns1 43200 IN A 220.127.116.11
ns2 43200 IN A 18.104.22.168
dns2 43200 IN A 22.214.171.124
ftp 43200 IN A 126.96.36.199
msg 43200 IN A 188.8.131.52
mx1 43200 IN A 184.108.40.206
mx2 43200 IN A 220.127.116.11
www 43200 IN A 18.104.22.168
sql 43200 IN A 22.214.171.124
test 43200 IN A 126.96.36.199
demo 43200 IN A 188.8.131.52
intranet 43200 IN A 184.108.40.206
@ 43200 IN A 220.127.116.11
Hope you can help.
October 22nd, 2001, 10:19 PM
A DNS lookup of sql.actconsult.net resolves to 18.104.22.168 instead of 22.214.171.124.
Change the order of your A records to:
They need higher preference than others.
October 26th, 2001, 05:40 AM
Re: Setting up subnets
You should not use A records for canonicals, but CNAMEs.
ns1 IN A IP-address
www IN CNAME ns1
sql IN CNAME ns1
October 26th, 2001, 05:59 AM
>> You should not use A records for canonicals, but CNAMEs
There no longer is such thing as CNAME one earth. Don't use CNAME, just multiple A records to do the same thing at all time.
CNAME lookup is unreliable and require more bandwith and resource. To lookup a CNAME, you must first lookup the A record of associates FQDN. That's a waste of resource.
When you are running your own mail server + authoratative DNS server yourself, using CNAME is strongly discouraged.
October 26th, 2001, 06:25 AM
Thanks guys, it was actually correctly configured. Somehow the name demon got switched off and then our DNS2 had incorrect information about the SQL subnet.
I'm slowly getting used to Linux configuration. Cheers!