Windows – DNS Glue Record Creation

domain-name-systemglue-recordwindowswindows-server-2008

I'm on Windows Server 2008. I'm using intoDNS to check I'm setting my DNS up correctly:

http://www.intodns.com/wewantogg.com

Everything looks fine for this domain except for the notice:

INFO: GLUE was not sent when I asked your nameservers for your NS records.This is ok but you should know that in this case an extra A record lookup is required in order to get the IPs of your NS records. The nameservers without glue are: 
209.126.137.108
209.62.64.46
You can fix this for example by adding A records to your nameservers for the zones listed above.

The name servers for this domain are:

ns12.zoneedit.com  ['209.62.64.46']   [TTL=7200] 
ns14.zoneedit.com  ['209.126.137.108']   [TTL=7200]

I've added them as a forward lookup zone in my servers DNS manager:

enter image description here

Is this correct? It's still saying glue records have not been found and I'd like to resolve this if possible.

Best Answer

You misread the warning message from intoDNS. It is not your DNS servers that doesn't return the correct glue records, it's the nameservers at zoneedit.com that does not return glue records.

In short: This is not your fault/problem, it's the good people at zoneedit.com's problem

Otherwise, very decent test result btw

Update: About the MX record
If you are not going to use this domain to receive mail, don't take note of the "error". You may however want to add an SPF record, to help prevent spammers abuse your domain name for mail spoofing purposes.

To add an SPF record, create a record of RR-type: TXT, with this value:

v=spf1 -all

This way you let SPF parsers know that all mail pretending to come from @wewantogg.com should be rejected as SPAM

If you plan to introduce a mail server for sending and receiving (for example an Exchange organization), you can add mx to be allowed:

v=spf1 mx -all

This way you let SPF parsers know that mail pretending to come from @wewantogg.com should be rejected as SPAM unless it is sent from your MX

Related Solutions

How to fix “no GLUE” problem with DNS lookups

Glue records are special A records which are needed when the name server for a DNS domain is itself in the same domain.

For example, if your domain is example.com and your name server is ns.example.com, you need to create a "glue" A record for ns.example.com in the next-highest DNS zone, in this case in the "com" zone. This should be done via your registrar.

This is required because DNS requests for name servers (NS records) are always answered with a name, not an IP.

Without a glue record, if a request were made for the A records www.example.com, a name server serving "com" would return the NS record for example.com as ns.example.com (not an IP), and the original request would have no way of being resolved, because any further attempt to resolve ns.example.com would merely refer back to ns.example.com.

DNS – How to Test Glue Record

Glue records only ever exist in the parent zone of a domain name.

Hence in the case of your example.org domain name, first find the .org name servers:

% dig +short org. NS
a0.org.afilias-nst.info.
a2.org.afilias-nst.info.
b0.org.afilias-nst.org.
b2.org.afilias-nst.org.
c0.org.afilias-nst.info.
d0.org.afilias-nst.org.

Then, for as many of these as you feel like testing, explicitly ask those name servers for the NS records for your domain:

% dig +norec @a0.org.afilias-nst.info. example.org. NS

You should get back the correct list of NS records in the "AUTHORITY SECTION". For any name servers that have correctly configured glue you should see those glue A (and/or AAAA) records appear in the "ADDITONAL SECTION".

Best Answer

Related Solutions

How to fix “no GLUE” problem with DNS lookups

DNS – How to Test Glue Record

Related Topic