Go Back   HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials > Linux Forums > HOWTO-Related Questions

Do you like HowtoForge? Please consider supporting us by becoming a subscriber.
 
 
Thread Tools Display Modes
Prev Previous Post   Next Post Next
  #11  
Old 13th January 2007, 05:25
wiremeister wiremeister is offline
Junior Member
 
Join Date: Sep 2006
Posts: 23
Thanks: 0
Thanked 1 Time in 1 Post
Default

I get the same information with one important difference. Ns3 and ns4 will resolve from outside the Comcast network (using another nameserver other than those assigned to us by Comcast). However, from a Linux machine here we get:

dig ns3.sheltiehosting.net
;; Got SERVFAIL reply from 68.87.85.98, trying next server

; <<>> DiG 9.3.2 <<>> ns3.sheltiehosting.net
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 41810
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;ns3.sheltiehosting.net. IN A

;; Query time: 1048 msec
;; SERVER: 68.87.69.146#53(68.87.69.146)
;; WHEN: Fri Jan 12 20:43:37 2007
;; MSG SIZE rcvd: 40

dig ns4.sheltiehosting.net gets the same result.

Using the same nameserver that you did (213.191.92.84) I get the identical results that you did today.


A dig @ns1.comcastbusiness.net within the Comcast network gets us this information:

dig @ns1.comcastbusiness.net any sheltiehosting.net

; <<>> DiG 9.3.2 <<>> @ns1.comcastbusiness.net any sheltiehosting.net
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9177
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 2

;; QUESTION SECTION:
;sheltiehosting.net. IN ANY

;; ANSWER SECTION:
sheltiehosting.net. 172800 IN NS ns3.sheltiehosting.net.
sheltiehosting.net. 172800 IN NS ns4.sheltiehosting.net.

;; AUTHORITY SECTION:
sheltiehosting.net. 172800 IN NS ns4.sheltiehosting.net.
sheltiehosting.net. 172800 IN NS ns3.sheltiehosting.net.

;; ADDITIONAL SECTION:
ns3.sheltiehosting.net. 172800 IN A 74.92.214.65
ns4.sheltiehosting.net. 172800 IN A 74.92.214.66

;; Query time: 2111 msec
;; SERVER: 208.39.158.1#53(208.39.158.1)
;; WHEN: Fri Jan 12 21:09:32 2007
;; MSG SIZE rcvd: 132

A Dig @ns2.comcastbusiness.net gets the same result.


Now a Dig @(IP):

dig @74.92.214.66 any sheltiehosting.net

; <<>> DiG 9.3.2 <<>> @74.92.214.66 any sheltiehosting.net
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34636
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 2

;; QUESTION SECTION:
;sheltiehosting.net. IN ANY

;; ANSWER SECTION:
sheltiehosting.net. 86400 IN SOA ns3.sheltiehosting.net. webmaster.sheltiehosting.net. 2007010702 28800 7200 604800 86400
sheltiehosting.net. 86400 IN A 74.92.214.65
sheltiehosting.net. 86400 IN NS ns4.sheltiehosting.net.
sheltiehosting.net. 86400 IN NS ns3.sheltiehosting.net.

;; ADDITIONAL SECTION:
ns3.sheltiehosting.net. 86400 IN A 74.92.214.65
ns4.sheltiehosting.net. 86400 IN A 74.92.214.66

;; Query time: 3 msec
;; SERVER: 74.92.214.66#53(74.92.214.66)
;; WHEN: Fri Jan 12 20:49:47 2007
;; MSG SIZE rcvd: 166

dig @74.92.214.65 any sheltiehosting.net

; <<>> DiG 9.3.2 <<>> @74.92.214.65 any sheltiehosting.net
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63260
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 2

;; QUESTION SECTION:
;sheltiehosting.net. IN ANY

;; ANSWER SECTION:
sheltiehosting.net. 86400 IN SOA ns3.sheltiehosting.net. webmaster.sheltiehosting.net. 2007010702 28800 7200 604800 86400
sheltiehosting.net. 86400 IN NS ns3.sheltiehosting.net.
sheltiehosting.net. 86400 IN NS ns4.sheltiehosting.net.
sheltiehosting.net. 86400 IN A 74.92.214.65

;; ADDITIONAL SECTION:
ns3.sheltiehosting.net. 86400 IN A 74.92.214.65
ns4.sheltiehosting.net. 86400 IN A 74.92.214.66

;; Query time: 0 msec
;; SERVER: 74.92.214.65#53(74.92.214.65)
;; WHEN: Fri Jan 12 20:50:26 2007
;; MSG SIZE rcvd: 166

I understand your assumption, that it would certainly look like named is down, and port 53 on both ns3 and ns4 are blocked. However, named is running, and port 53 is open as evidenced. Both ns3 and ns4 have the same information.

I haven't heard back from Comcast DNS as of yet, though I've tried to reach them (It will be Monday before I can try again. They work M-F 9-5 only). After the traceroutes I have done, and one other done by a Comcast Tech Support person, it would appear that something in one particular server enroute to us here has a problem. All traceroutes stop (time out) at the same server two hops before arriving here (originating outside the Comcast network). This is what we've asked them to look at.

One interesting thing is that sheltiehosting.org and .com will resolve from inside and outside the Comcast network. Where .net will not. I'm almost to the point of changing the nameservers to a .com just to see if it makes a difference. I'm beginning to believe it just might.

Thanks for the clarification on the glue records.

Last edited by wiremeister; 13th January 2007 at 05:35.
Reply With Quote
Sponsored Links
 

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +2. The time now is 04:05.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.