Re: PLUG website DNS issues

Top Page
Attachments:
Message as email
+ (text/plain)
Delete this message
Reply to this message
Author: Mike
Date:  
To: plug-discuss
Subject: Re: PLUG website DNS issues
Jeremy C. Reed wrote:

>This does not seem to be any DNS issue.
>
>The name servers responsible are (according to NS2.DERU.NET. and
>NS1.DERU.NET.):
>
>ns2.sequoia.net. 68.14.243.57
>ns3.LuftHans.com. 68.110.171.226
>
>ns3.LuftHans.com. and ns2.sequoia.net. returns IP 66.98.190.6 for
>plug.phoenix.az.us.
>
>Anyways, I can get to the website fine.
>
> Jeremy C. Reed
>
>                 BSD News, BSD tutorials, BSD links
>                http://www.bsdnewsletter.com/

>
>
>
>

I'm very amature at DNS so I don't know for sure, but it Appears to be a
DNS issue on plug.phoenix.az.us's end to me..

For one, the SOA is set at 'nina. hostmaster.LuftHans.com.'. (what is
nina. supposed to resolve to?)
---------------------------------------------------------------------------------------------
dig SOA plug.phoenix.az.us

; <<>> DiG 9.2.4 <<>> SOA plug.phoenix.az.us
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58897
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2

;; QUESTION SECTION:
;plug.phoenix.az.us.            IN      SOA


;; ANSWER SECTION:
plug.phoenix.az.us.     600     IN      SOA     nina. 
hostmaster.LuftHans.com. 2004041002 28800 86400 86400 86400


;; AUTHORITY SECTION:
plug.phoenix.az.us.     600     IN      NS      ns3.LuftHans.com.
plug.phoenix.az.us.     600     IN      NS      ns2.sequoia.net.


;; ADDITIONAL SECTION:
ns2.sequoia.net.        171250  IN      A       68.14.243.57
ns3.LuftHans.com.       171250  IN      A       68.110.171.226


;; Query time: 165 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Apr 20 18:32:15 2005
;; MSG SIZE rcvd: 178
-------------------------------------------------------------------------------------



And it's falling back on deju's name servers for responses without a
glue record. I'm no deligated domain master or anything, but I believe
you need to glue the domain to the authoritative parent.

------------------------------------------------------------------------------------
dig NS plug.phoenix.az.us

; <<>> DiG 9.2.4 <<>> NS plug.phoenix.az.us
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30381
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 2

;; QUESTION SECTION:
;plug.phoenix.az.us.            IN      NS


;; ANSWER SECTION:
plug.phoenix.az.us.     600     IN      NS      ns3.LuftHans.com.
plug.phoenix.az.us.     600     IN      NS      ns2.sequoia.net.


;; ADDITIONAL SECTION:
ns2.sequoia.net.        172800  IN      A       68.14.243.57
ns3.LuftHans.com.       172800  IN      A       68.110.171.226


;; Query time: 4807 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Apr 20 18:06:25 2005
;; MSG SIZE rcvd: 127
----------------------------------------------------------------------------------------

In either case, it is falling back on deju's name servers for responses.
It should be told to do that if that is what you want it to do.
(basically, plug.phoenix.az.us isn't directing the resolution correctly)
I don't quite know how they are doing the sub domain since I think there
is a few ways you could go about it.... But depending on that, it still
isn't right in the configuration somehow.


-Mike
---------------------------------------------------
PLUG-discuss mailing list -
To subscribe, unsubscribe, or to change you mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss