TS3 DNS must be down

[KRDucky]

The Fragging Frogs TS3 Server DNS must be down. Can't ping it or connect to it.

[KRDucky]

Here is the results from a DNS check
http://dnscheck.pingdom.com/?domain=...4232281&view=1

There is something wrong with the nameserver and SOA.

• Name server ns4.microsoftinternetsafety.net (157.56.78.73) not authoritative for frogs.servegame.com.
• Name server ns3.microsoftinternetsafety.net (157.56.78.93) not authoritative for frogs.servegame.com.

SOA errors:

• SOA MNAME for frogs.servegame.com (ns3.microsoftinternetsafety.net) is not authoritative.
• Delivery over IPv4 to hostmaster@microsoftinternetsafety.net could not be done.
• Failed to deliver email for SOA RNAME of frogs.servegame.com (hostmaster.microsoftinternetsafety.net) using hostmaster@microsoftinternetsafety.net.

Delegation
Begin testing delegation for frogs.servegame.com.
Name servers listed at parent: ns3.microsoftinternetsafety.net,ns4.microsoftinternetsafety.net
Name servers listed at child: ns3.microsoftinternetsafety.net,ns4.microsoftinternetsafety.net
No IPv6 name servers found.
Parent glue for frogs.servegame.com found: ns3.microsoftinternetsafety.net (157.56.78.93)
Checking glue for ns3.microsoftinternetsafety.net (157.56.78.93).
Parent glue for frogs.servegame.com found: ns3.microsoftinternetsafety.net (157.56.78.93)
Nameserver
Done testing delegation for frogs.servegame.com.
Begin testing name server ns3.microsoftinternetsafety.net.
Begin testing host ns3.microsoftinternetsafety.net.
Begin testing address 157.56.78.93.
Done testing address 157.56.78.93.
Done testing host ns3.microsoftinternetsafety.net.
Name server ns3.microsoftinternetsafety.net (157.56.78.93) answers queries over UDP.
Name server ns3.microsoftinternetsafety.net (157.56.78.93) answers queries over TCP.
Name server ns3.microsoftinternetsafety.net (157.56.78.93) is recursive.
Name server ns3.microsoftinternetsafety.net (157.56.78.93) not authoritative for frogs.servegame.com.
Done testing name server ns3.microsoftinternetsafety.net.
Begin testing name server ns4.microsoftinternetsafety.net.
Begin testing host ns4.microsoftinternetsafety.net.
Begin testing address 157.56.78.73.
Done testing address 157.56.78.73.
Done testing host ns4.microsoftinternetsafety.net.
Name server ns4.microsoftinternetsafety.net (157.56.78.73) answers queries over UDP.
Name server ns4.microsoftinternetsafety.net (157.56.78.73) answers queries over TCP.
Name server ns4.microsoftinternetsafety.net (157.56.78.73) is recursive.
Name server ns4.microsoftinternetsafety.net (157.56.78.73) not authoritative for frogs.servegame.com.
Done testing name server ns4.microsoftinternetsafety.net.
Consistency
Begin testing zone consistency for frogs.servegame.com.
SOA at address 157.56.78.93 has serial 1.
SOA at address 157.56.78.73 has serial 1.
All SOA records have consistent serial numbers.
All SOA records are consistent among all name servers.
Done testing zone consistency for frogs.servegame.com.
SOA
Begin testing SOA parameters for frogs.servegame.com.
Found SOA record for frogs.servegame.com.
Begin testing host ns3.microsoftinternetsafety.net.
Begin testing address 157.56.78.93.
Done testing address 157.56.78.93.
Done testing host ns3.microsoftinternetsafety.net.
SOA MNAME for frogs.servegame.com valid (ns3.microsoftinternetsafety.net).
SOA MNAME for frogs.servegame.com (ns3.microsoftinternetsafety.net) listed as NS.
SOA MNAME for frogs.servegame.com (ns3.microsoftinternetsafety.net) is not authoritative.
Begin testing email address hostmaster@microsoftinternetsafety.net.
Mail exchangers for hostmaster@microsoftinternetsafety.net found microsoftinternetsafety.net.
Begin testing host microsoftinternetsafety.net.
Begin testing address 131.107.221.40.
Done testing address 131.107.221.40.
Done testing host microsoftinternetsafety.net.
Begin testing mail server microsoftinternetsafety.net (131.107.221.40) with hostmaster@microsoftinternetsafety.net.
Failed to connect to microsoftinternetsafety.net (131.107.221.40).
Done testing mail server microsoftinternetsafety.net (131.107.221.40) with hostmaster@microsoftinternetsafety.net.
Delivery over IPv4 to hostmaster@microsoftinternetsafety.net could not be done.
Delivery over IPv6 to hostmaster@microsoftinternetsafety.net could not be done.
Done testing email address hostmaster@microsoftinternetsafety.net.
Failed to deliver email for SOA RNAME of frogs.servegame.com (hostmaster.microsoftinternetsafety.net) using hostmaster@microsoftinternetsafety.net.
SOA TTL for frogs.servegame.com OK (155792) - recommended >= 3600.
SOA refresh for frogs.servegame.com too small (10800) - recommended >= 14400.
SOA retry for frogs.servegame.com too small (15) - recommended >= 3600.
SOA expire for frogs.servegame.com OK (604800) - recommended >= 604800.
SOA minimum for frogs.servegame.com OK (10800) - recommended between 300 and 86400.
Done testing SOA parameters for frogs.servegame.com.
Connectivity
Begin testing connectivity for frogs.servegame.com.
Name server 157.56.78.93 announced by: 8075
Name server 157.56.78.73 announced by: 8075
Zone announced by ASN: 8075
Zone announced by only one ASN (1).
Zone announced by IPv6 ASN:
Zone announced by only one IPv6 ASN (0).
Done testing connectivity for frogs.servegame.com.
DNSSEC
Begin testing DNSSEC for frogs.servegame.com.
Did not find DS record for frogs.servegame.com at parent.
Servers for frogs.servegame.com have consistent extra processing status.
Did not find DNSKEY record for frogs.servegame.com at child.
No DNSKEY(s) found at child, other tests skipped.
Done testing DNSSEC for frogs.servegame.com.
Test completed for zone frogs.servegame.com.

[KRDucky]

I could use the nameservers listed below to performe recursive queries. It may be that I am wrong but the chances of that are low. You should not have nameservers that allow recursive queries as this will allow almost anyone to use your nameservers and can cause problems. Problem record(s) are:
157.56.78.73
157.56.78.93

ERROR: looks like you have lame nameservers. The following nameservers are lame:
157.56.78.73
157.56.78.93

WARNING: Not all of your nameservers are in different subnets

WARNING: Single point of failure

Your SOA RETRY value is: 15. That is NOT OK

ERROR: I could not get any A records for www.frogs.servegame.com!

(I only do a cache request, if you recently added a WWW A record, it might not show up here.)

Some of your nameservers failed to return an A record for your domain. This is probably not what you want. The following nameservers did not return an A record:

ns3.microsoftinternetsafety.net
ns4.microsoftinternetsafety.net

Some of your nameservers provide recursive lookups. This is bad since it could be used to poison caches or other DNS attacks. The following nameservers indicated that they support recursive lookups:

ns3.microsoftinternetsafety.net
ns4.microsoftinternetsafety.net

Some of your nameservers did not respond authoritatively for your domain. The following nameservers did not respond authoritatively:

ns3.microsoftinternetsafety.net
ns4.microsoftinternetsafety.net

You have only 2 nameservers, which is the minimum allowed. There is a chance that they could both fail simultaneously. Although not necessary, you should consider increasing the number of nameservers to 3.

Your nameservers are all on the same class C IP namespace. This is an indication (but not proof) that they may be co-located, which could be a risk should the internet connection to that location fail.

Your SOA serial number is 1. This does not match the recommended format of YYYYMMDDnn [RIPE-203]. This is not necessarily a problem as long as your DNS admin knows what they are doing.

Your SOA retry value is 15 secs. This is the time a slave nameserver will wait if an attempt to contact a primary nameserver failed before it tries again. This seems low. It may cause unnecessary load during a network outage between a slave and master DNS server.

Just a suggestion but perhaps moving to OpenDNS may be more fortuitous?

[Activate: AMD]

yes, see sub's post here:

If you're having trouble connecting to TS3 it's not just you. The following link will explain why frogs.servegame.com isn't working for everyone.

https://www.noip.com/blog/2014/06/30...soft-takedown/

Fortunately my asus router offers free ddns from asus, you can use the following hostname to connect if frogs.servegame.com doesn't work for you. Both hostnames should work, but the asus hostname will work for sure. Hopefully ms and no-ip get things settled soon.

I didn't even get an email from No-IP about any of this and I'm a paying customer.

fraggingfrogs.asuscomm.com

I apologize for the inconvenience and any heartache and sleepless nights this may have caused.

No-IP has been inexpensive (or free) and reliable for years. And forgive me if I misunderstand OpenDNS's product, but what No-IP does is provide the domain name forwarding for a dynamic IP for people who want to connect from the outside. It is NOT a DNS server that you point everything to resolve domain names outside your network, which is what OpenDNS looks like.

[KRDucky]

Ah, you are correct in What OpenDNs does. I was under the understanding that it also provided the NO-IP services. According to Spiceworks, OpenDNS also provides NO-IP services.

Although, so is Dynect DNS.
http://dyn.com/managed-dns/

And DNSMadeEasy
www.dnsmadeeasy.com

[Lenny]

frogs.ddns.net also now points to Brandito's TS server