Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

NS records at the parent servers (No Glue)

Status
Not open for further replies.

Edward999

Programmer
Dec 26, 2002
112
MY

Hi,

Can i know why i'm getting "No Glue" when i enter my domain alpinetower.com.my at the DNSreport.com

I have a DNS server running on my Linux Redhat 8.0 machine. I'm hosting this domain at my office.

I really have no idea how to solve this....Please help

Thanks for any reply.
 

oops...sorry the domain is "alpinetower.com.my"

Thanks for your fast reply.

edward
 
Well, that appears to be delegated to ;

alpinetower.com.my. 86400 IN NS ns1.plexus.net.
alpinetower.com.my. 86400 IN NS ns2.plexus.net.

But if I query both of those for NS records then I get different answers;

[chris@uranium chris]$ dig alpinetower.com.my ns @ns2.plexus.net +short
ns2.hicomcom.com.
ns1.hicomcom.com.
[chris@uranium chris]$ dig alpinetower.com.my ns @ns1.plexus.net +short
ns2.plexus.net.
ns1.plexus.net.

However, a trace shows that the parent zone at ns6.jaring.my shows the name servers to be listed as;

lpinetower.com.my. 86400 IN NS ns1.plexus.net.
alpinetower.com.my. 86400 IN NS ns1.hicom-net.com.

The 'glue' records are placed in the parent zone so that the name servers can be resolved to query the servers for other RR's. In this case ns6.jaring.my has a glue record that delegates alpinetower.com.my to ns1.hicom-net.com but doesn't provide an A record to resolve it.

It's all pretty messued up really. Your delegation data doesn't match your name server data in the zones and two different servers are giving two different answers.

In short, the parent zone should have a delegation for your domain pointing to two name servers. Those two name servers should have NS records in their zone files that matches the delegation data. Basically, it should all match.

Chris.

**********************
Chris A.C, CCNA, CCSA
**********************
 
Thanks for your fast response. Look like my DNS quite messy.
Actually my company only have one DNS server which is ns1.hicom-net.com and my secondary DNS is ns1.plexus.net.

I really don't know where to change and how to make it right.

My named.conf as below:

options{
directory "/var/named";
forwarders {
202.47.162.3;
};
};

zone "." {
type hint;
file "named.root";
};

zone "localhost" {
type master;
file "localhost";
};

zone "0.0.127.in-addr.arpa" {
type master;
file "127.0.0";
};

zone "195.44.93.219.in-addr.arpa" {
type master;
file "219.93.44.195";
};

zone "198.44.93.219.in-addr.arpa" {
type master;
file "219.93.44.198";
};

zone "alpinetower.com.my" {
type master;
file "alpinetower.com.my";
};



Zone file for my DNS server 219.93.44.195 as below:


195.44.93.219.in-addr.arpa. SOA ns1.hicom-net.com. hostmaster.hicom-net.com. (
2003061600 ; Serial
43200 ; Refresh
7200 ; Retry
2419200 ; Expire
172800 ) ; Minimum TTL

195.44.93.219.in-addr.arpa. NS ns1.hicom-net.com.

195.44.93.219.in-addr.arpa. NS ns1.plexus.net.

195.44.93.219.in-addr.arpa. PTR ns1.hicom-net.com.



Zone file for alpinetower.com.my as below:

alpinetower.com.my. SOA ns1.hicom-net.com. hostmaster.hicom-net.com. (
2003061600 ; Serial
43200 ; Refresh
7200 ; Retry
2419200 ; Expire
172800 ) ; Minimum TTL

alpinetower.com.my. NS ns1.hicom-net.com.

alpinetower.com.my. NS ns1.plexus.net.

alpinetower.com.my. MX 10 mail.alpinetower.com.my.


A 219.93.44.198
ns1.hicom-net.com. A 219.93.44.195
ns1.plexus.net. A 202.47.162.3
mail.alpinetower.com.my. A 219.93.44.198


Zone file for my web server is:


198.44.93.219.in-addr.arpa. SOA ns1.hicom-net.com. hostmaster.hicom-net.com. (
2003061600 ; Serial
43200 ; Refresh
7200 ; Retry
2419200 ; Expire
172800 ) ; Minimum TTL

198.44.93.219.in-addr.arpa. NS ns1.hicom-net.com.

198.44.93.219.in-addr.arpa. NS ns1.plexus.net.

198.44.93.219.in-addr.arpa. PTR
Thanks for any reply.

edward
 
Well, I would do the following ..

1. I would speak to my registrar about the delegation data not having a A record for ns1.hicom-net.com and get them to fix that so that the glue works as it should.

Hang on ... it's working now ..

[chris@uranium chris]$ dig ns1.hicom-net.com @ns7.jaring.my
<snip>
;; ANSWER SECTION:
ns1.hicom-net.com. 37517 IN A 219.93.44.195

2. I would speak to the DNS admin at plexus.net and sort out your master/slave set up. Your server has different data to that of ns1.plexus.net and so I'm guessing that both are set up as masters and the plexus server is not slaving off you!

ERROR: Your nameservers disagree as to which version of your DNS is the latest (2003061600 versus 2004060508). This is OK if you have just made a change recently, and your secondary DNS servers haven't yet received the new information from the master. I will continue the report, assuming that 2004060508 is the correct serial #. The serial numbers reported by each DNS server are:
219.93.44.195: 2003061600
202.47.162.3: 2004060508

Chris.

**********************
Chris A.C, CCNA, CCSA
**********************
 

Thanks Chris for your fast response.

Yes you are right. I checked with DNS admin at plexus.net, they said the ip 202.47.162.3 is thier master and 202.47.162.4 is thier slave dns.

So should i change my secondary dns to 202.47.162.4 If yes do i have to make sure both of my serial# the same for my primary and secondary dns server.

Thanks for any reply.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top