|
Thread Index [isp-dns] Re: Domain not resolving properly via http?
This wont help, but will save you in the future. Always outsource one auth ns, incase of internal network failure, you wont loose your DNS caches and make even MORE of a downtime. Dave Smulsky Senior Network Admin dave@... www.thehostworks.com ----- Original Message ----- From: "Alex Kamantauskas" <alexk@...> To: <isp-dns@isp-dns.com> Sent: Tuesday, November 05, 2002 10:24 AM Subject: [isp-dns] Re: Domain not resolving properly via http? On Tue, 5 Nov 2002, Michael Kleinert wrote: > However, all other domains I have on this particular reseller account > with the same configuration and NS error resolve properly. > Additionally, this domain resolves properly for ftp, for email, and to > reach the domain control panel. > Hmm... there appears to be a myriad of problems. First, the roots have the following servers as authoritative for "truckalarm.com" TRUCKALARM.COM nameserver = NS1.SMOOTHSERVERS.COM TRUCKALARM.COM nameserver = NS2.SMOOTHSERVERS.COM However, the only A records for these names appear in the gtld servers: root/ns1:/ # dig @a.gtld-servers.net ns1.smoothservers.com a ;; ANSWER SECTION: ns1.smoothservers.com. 2D IN A 66.227.7.127 root/ns1:/ # dig @a.gtld-servers.net ns2.smoothservers.com a ;; ANSWER SECTION: ns2.smoothservers.com. 2D IN A 66.227.7.128 The auth servers for smoothservers.com have no A records for those domain names: root/ns1:/ # dig @ns3.dnshotel.com ns1.smoothservers.com a ; <<>> DiG 8.1 <<>> @ns3.dnshotel.com ns1.smoothservers.com a ; (1 server found) ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 10 A records need to be set up in the smoothservers.com zone file for these nameservers. Now, in the truckalarm.com zone file, you have the following NS records listed: root/ns1:/ # dig @ns3.dnshotel.com truckalarm.com ns ;; ANSWER SECTION: truckalarm.com. 4H IN NS ns4.dnshotel.com. truckalarm.com. 4H IN NS ns3.dnshotel.com. Which have the IP addresses 66.227.7.121 and 66.227.7.122, respectively. In effect, the root server entry is telling the world to go to nameservers that don't exist for information concerning "truckalarm.com" Now, it would appear that the only reason "truckalarm.com" resolves at all is because (and this is an assumption) ns3.dnshotel.com is also answering queries made to 66.227.7.127 (the phanton "ns1.smoothservers.com" - at least, I was able to perform a DNS query directed to that IP address) The NS records within the zone need to match the NS records of the parent delegation. If you are setting up virtual nameservers, which is what I think you are trying to do, then the NS records still need to match. For instance, I have a nameserver that listens on 10.0.0.1 - this is ns1.myns.com. A customer comes along and wants me to do DNS, but they want their name on the NS records at the roots. Easily done. I create a virtual interface on the NS, address is 10.0.0.2, and call it "ns1.custns.com", and register the domain name with that server. If I do this, I must have the NS RR in the customer's zone file say "ns1.custns.com", since that matches the parent delegation. > Additionally, I can confirm that the webspace is reachable via an > alternate path of: > > http://thor.dnshotel.com/~jack > Now, all that above being said, I think this is a different problem. I was able to get to the web site at <http://www.truckalarm.com/>. I did a "View source" and it the entire contents of the web site was the single line "<html>". Meanwhile, <http://thor.dnshotel.com/~jack> gets me to the web page in question. I think what is going on is that you have a web configuration error, and that HTTP packets destined to <http://www.truckalarm.com/> are not being directed over to <http://thor.dnshotel.com/~jack> > Can anybody help in determining what is going on? > > Many thanks. > > Mike > > > -- /ak
Thread Index |
|
