Technitium delivers no IP for "www.androidmagazine.eu"

[myssv]

Hi there,
I use Technitium as a DNS Server with no forwarding.

I got no IP for the adress, but the DNS Server on my FritzBox got one.

Sorry for my bad english. I hope you could understand!

`PS C:\Users\Volke> nslookup www.androidmagazine.eu
Server: technitium.fritz.box
Address: 192.168.115.101

*** www.androidmagazine.eu wurde von technitium.fritz.box nicht gefunden: Server failed.
PS C:\Users\Volke> nslookup www.androidmagazine.eu 192.168.115.1
Server: fritz.box
Address: 192.168.115.1

Nicht autorisierende Antwort:
Name: www.androidmagazine.eu
Address: 46.36.41.14
`

[ShreyasZare]

Thanks for the post. The domain is resolving well here. Please check if there are any error logs from the Logs section on the DNS admin panel to know why it failed to resolve. Share any error log you see here if you need help with it.

Also, please test using the DNS Client tab on the admin panel instead of using thee nslookup command since it gives you more info when resolution fails.

[myssv]

{
"Metadata": {
"NameServer": "technitium (127.0.0.1)",
"Protocol": "Udp",
"DatagramSize": "153 bytes",
"RoundTripTime": "199.51 ms"
},
"EDNS": {
"UdpPayloadSize": 1232,
"ExtendedRCODE": "ServerFailure",
"Version": 0,
"Flags": "None",
"Options": [
{
"Code": "EXTENDED_DNS_ERROR",
"Length": "64 bytes",
"Data": {
"InfoCode": "NoReachableAuthority",
"ExtraText": "Recursion stack limit reached for www.androidmagazine.eu. A IN"
}
},
{
"Code": "EXTENDED_DNS_ERROR",
"Length": "30 bytes",
"Data": {
"InfoCode": "CachedError",
"ExtraText": "www.androidmagazine.eu. A IN"
}
}
]
},
"DnsClientExtendedErrors": [
{
"InfoCode": "NoReachableAuthority",
"ExtraText": "technitium (127.0.0.1) returned RCODE=ServerFailure for www.androidmagazine.eu. A IN"
}
],
"Identifier": 18570,
"IsResponse": true,
"OPCODE": "StandardQuery",
"AuthoritativeAnswer": false,
"Truncation": false,
"RecursionDesired": true,
"RecursionAvailable": true,
"Z": 0,
"AuthenticData": false,
"CheckingDisabled": false,
"RCODE": "ServerFailure",
"QDCOUNT": 1,
"ANCOUNT": 0,
"NSCOUNT": 0,
"ARCOUNT": 1,
"Question": [
{
"Name": "www.androidmagazine.eu",
"Type": "A",
"Class": "IN"
}
],
"Answer": [],
"Authority": [],
"Additional": [
{
"Name": "",
"Type": "OPT",
"Class": "1232",
"TTL": "0 (0s)",
"RDLENGTH": "102 bytes",
"RDATA": {
"Options": [
{
"Code": "EXTENDED_DNS_ERROR",
"Length": "64 bytes",
"Data": {
"InfoCode": "NoReachableAuthority",
"ExtraText": "Recursion stack limit reached for www.androidmagazine.eu. A IN"
}
},
{
"Code": "EXTENDED_DNS_ERROR",
"Length": "30 bytes",
"Data": {
"InfoCode": "CachedError",
"ExtraText": "www.androidmagazine.eu. A IN"
}
}
]
},
"DnssecStatus": "Disabled"
}
]
}

[ShreyasZare]

Thanks for the details. The Recursion stack limit reached error message means that some name server keep on returning list of same name servers causing the resolver to go in loops. Since the domain is resolving well from multiple places that I have tested, it seems like your ISP or some network middlebox is interfering with DNS queries and causing this issue.

The mitigation you can do is create a Conditional Forwarder zone for androidmagazine.eu and use any public DNS provider as the forwarder. That should allow the domain name to resolve indirectly.

[myssv]

ok, thanks a lot for your help.

[ShreyasZare]

You're welcome.