-
Notifications
You must be signed in to change notification settings - Fork 192
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't resolve query #29
Comments
please enable tcp dns query in your dns server. To test if your dns server is working
|
; <<>> DiG 9.9.5-3ubuntu0.8-Ubuntu <<>> -p 10053 +vc @192.168.254.111 mirror.webtatic.com ;; OPT PSEUDOSECTION: ;; ANSWER SECTION: ;; AUTHORITY SECTION: ;; Query time: 0 msec dig just returns fine but when I use the dns proxy it just can't resolve query. |
So the line it is failing is on here https://github.com/henices/Tcp-DNS-proxy/blob/master/tcpdns.py#L271 both the test_ipv4 and test_ipv6 are having values of false. Can I know what the Reply_code values mean? Because the Reply_code value of mine is 0 |
see
reply code 0 means No error condition. In your config file Please send me pcap file (use wireshark) for more information. |
So my setup is that my DNS server and proxy is on the same machine
{
"socket_timeout": 20,
"host": "192.168.254.111",
"port": 53,
"tcp_dns_server": ["192.168.254.111:10053"],
"udp_dns_server": ["192.168.254.111:10053"],
"enable_server_switch": true,
"speed_test" : false,
"enable_lru_cache": false,
"lru_cache_size" : 500,
"udp_mode" : true,
"daemon_process" : false,
"internal_dns_server": ["127.0.0.1:53"],
"internal_domain":["intra"],
"private_host" : {"*google.com": "203.117.34.162"}
}
I just let my DNS server to listen on port 10053 and the proxy on 53. The issue is that it can't resolve certain queries like this kind of nslookup
nslookup -query=A mirror.webtatic.com
Is there wrong with my setup?
Any help is appreciated.
The text was updated successfully, but these errors were encountered: