His dns is comming back clean:
QUESTIONS:
www.fetishdyke.net, type = A, class = IN
ANSWERS:
->
www.fetishdyke.net
canonical name = fetishdyke.net
ttl = 14303 (3h58m23s)
-> fetishdyke.net
internet address = 209.51.139.26
ttl = 14297 (3h58m17s)
AUTHORITY RECORDS:
-> fetishdyke.net
nameserver = ns2.maxxxhosting.com
ttl = 14297 (3h58m17s)
-> fetishdyke.net
nameserver = ns2.maxxxhosting.net
ttl = 14297 (3h58m17s)
-> fetishdyke.net
nameserver = ns1.maxxxhosting.com
ttl = 14297 (3h58m17s)
-> fetishdyke.net
nameserver = ns1.maxxxhosting.net
ttl = 14297 (3h58m17s)
ADDITIONAL RECORDS:
-> ns2.maxxxhosting.com
internet address = 209.51.139.28
ttl = 172703 (1d23h58m23s)
-> ns2.maxxxhosting.net
internet address = 209.51.139.27
ttl = 172703 (1d23h58m23s)
-> ns1.maxxxhosting.com
internet address = 209.51.139.29
ttl = 172703 (1d23h58m23s)
-> ns1.maxxxhosting.net
internet address = 209.51.139.26
ttl = 172703 (1d23h58m23s)
The name servers match the whois ( which hasn't been updated in a while ) . So unless the host of the TGP is doing something wierd ( like ignoring TTLs ) , doubt DNS is the problem.