Replies: 2 comments 7 replies
-
|
Thanks for the post. The info is not sufficient to figure out the issue. Please share screenshot of both the zones showing the relevant records. Also share the output of the queries you do for tests. It would be best if you test this using DNS Client tool on the DNS admin panel instead of using nslookup command since the DNS Client output shows the entire response details which helps debugging such issues. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Beta Was this translation helpful? Give feedback.
7 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment


Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I have a construct, where a first DNS-Server with a primary Zone including a record for Split Horizon App is located in one site.
In another site I have a second DNS-Server with a Forwarder Zone pointing to the first DNS Server.
This is working well, if I query for records with failover app.
But If I try to query the second server for a record of the split horizon app, I get an empty response of the second server to my client. In the log of the primary server I see the correct answer.
Also if I use the nslookup command on the second server to directly query the first server, I get the correct answer.
My config for the record on the first server is as follows:
{
"10.10.0.0/16": [
"10.10.0.18"
],
"10.9.0.0/16": [
"10.9.20.18"
]
}
What could be the reason, that is doesn't work for split horizon records, while working for failover records, when querying the second server?
Regards,
Thomas
Beta Was this translation helpful? Give feedback.
All reactions