DNS forwarder not working on query mode
-
Yeah. You also have to do a domain override for the in-addr.arpa domain for those addresses.
-
@derelict I have set a domain override 10.45.33.in-addr.arpa pointed to DNS 10.45.1.60 but still not working... is this current config correct?
-
@la6er said in DNS forwarder not working on query mode:
is this current config correct?
I don't see any config.
-
this is how i have set my domain override at this moment
the second entrie is working fine everything x.sduop.net is resolving correctly through 10.45.1.60, however reverse is not working
I am currently testing with this host as example
n00214wsw7ws102.sduop.net
server: pfsense3.geq.net
Address: 10.30.251.59Non-authoritative response:
name: n00214wsw7ws102.sduop.net
Address: 10.45.33.201_______________________________________________-
10.45.33.201
Servidor: pfsense3.geq.net
Address: 10.30.251.59*** pfsense3.geq.net do not find 10.45.33.201: Non-existent domain
-
@derelict said in DNS forwarder not working on query mode:
in-addr.arpa
Shouldn't it be 33.45.10.in-addr.arpa?
-
^exactly a ptr zone for a network of 10.45.33 would be as KOM stated.. Your way would be for a network 33.45.10
-
Thanks a lot guys !! it is working now as expected ! I really appreciate your help !
-
I would prob adjust your NS you have listed in pfsense - pointing to NS that can not resolve the same stuff is destined for grief..
If your going to forward, all the NS you forward to should resolve the same stuff. If your NS can not both resolve the same stuff I would just pick one, and then use overrides for domains a different NS can resolve.
-
@johnpoz Thanks a lot, I do have 2 DNS server which resolve different stuff... so I am going with the domain override option and pick 1 as a general DNS on the forwarder
-
@kom Well, yeah. Just pointing in the right direction.
-
@derelict Haha I didn't actually mean to reply to you, but to him. No idea how that happened.
