Domain not resolving

[TheBiaatch]

hi, Ive created a new domain and I got several errors, searched trough all this forum and I really want this to work, here is the errors I get:

http://www.dnsstuff.com/tools/dnsreport.ch?domain=warezteacher.com

[root@server ~]# dig @a.gtld-servers.net warezteacher.com

; <<>> DiG 9.3.3rc2 <<>> @a.gtld-servers.net warezteacher.com
; (2 servers found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53516
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 0

;; QUESTION SECTION:
;warezteacher.com. IN A

;; AUTHORITY SECTION:
warezteacher.com. 172800 IN NS ns1.twilight.ws.
warezteacher.com. 172800 IN NS ns2.twilight.ws.

;; Query time: 56 msec
;; SERVER: 192.5.6.30#53(192.5.6.30)
;; WHEN: Tue Aug 14 10:25:57 2007
;; MSG SIZE rcvd: 81

How do I fix this? If someone can fix this I'm willing to give a donation.

 

[nobaloney]

Here are the various errors/warnings you're getting, and what to do about them:

Glue at Parent Nameservers: This could be a bug in the dnsstuff software; there's no reason why they should check any server gtld-servers.net for nameservers in ws domains. They should be checking the dns.ws nameservers.

Open DNS Servers: The nameservers at twilight.ws are open nameservers; that means they're set as caching nameservers. If they're your nameservers and hosted on your system(s) then you need to disable caching on your nameserver. Information is all over the 'net and all over these forums as well so I won't repeat it here. However, if you're relying on the same nameserver to support DNS resolution for your server(s) you'll have to use a different server. You should NOT use the same nameservers for both caching and authoritative resolving.

Number of Nameservers: ns2.twilight.ws doesn't resolve, so you only have one nameserver. If it resolved to the same IP# or an IP# in the same class, you'd also get this error.

Nameservers on Separate Class Cs: You need at least two nameservers, on two machines, on two different networks, to avoid this warning. If you don't have two servers you should find someone to handle your slave DNS.

Single Point of Failure: The same problem as Nameservers on Separate Class Cs.

Jeff