DNS random problems.
-
Im using 2.0-BETA5 (i386)
built on Sun Jan 16 21:23:13 EST 2011With dual WAN balance and one LAN.
Im having random problems with pfsense dns, when i put active dns forwarder a machine can browse for a time but in some moment its not possible anymore (the connections for msn or a download remain, but dns does not work), if a do a dhcp release /renew in the client the problem fix for another while.
To discard my isp dns i try for a day a machine directly connected to the modem without problems.
-
I have similar dns issues. After a couple days uptime the dns forwarder stops working for some reason, I have tried renewing the router's wan dhcp lease to fix it and that doesn't seem to work every time. I reboot the pfsense box and that fixes it.
-
To be honest unless your running the latest snap, not sure what your wanting to let someone know about or what advice you want other than update to current snap, and then if same problem then can troubleshoot issue.
Your snap is like 2 weeks old.
I show this is current snap for the i386 build
2.0-BETA5 (i386)
built on Sat Jan 29 01:09:59 EST 2011You are on the latest version.
edit: "if a do a dhcp release /renew in the client the problem fix for another while. "
this makes no sense what so ever. And kind of points to something other than a dns issue to be sure.. If you saying your client still has connectivity, ie active lease and just dns is not working.. getting a new lease pointing back to your pfsense box for dns would have nothing to do with the dns forwarding process crashing on your pfsense box.
Lets see the issuse, do query to your pfsense box dns and show the response you get, is it servfail? what? But your able to talk to your pfsense box.
Then renew the lease and try the same query - post results, you now say it works?? That makes no sense at all!
-
edit: "if a do a dhcp release /renew in the client the problem fix for another while. "
this makes no sense what so ever. And kind of points to something other than a dns issue to be sure.. If you saying your client still has connectivity, ie active lease and just dns is not working.. getting a new lease pointing back to your pfsense box for dns would have nothing to do with the dns forwarding process crashing on your pfsense box.
ok maybe can be the dhcp server instead?
Lets see the issuse, do query to your pfsense box dns and show the response you get, is it servfail? what? But your able to talk to your pfsense box.
the way that i suspect its dns its because i lost any resolve, including "ping pfsense.mylan.local" i can access by ip but not resolve anything
Then renew the lease and try the same query - post results, you now say it works?? That makes no sense at all!
when the issue happens i renew the ip (or unplug and plug the lan cable of the client) and works for another while, its not the pc because i have try in different pcs with different os, and later connected directly to my isp without pfsense and the problem not occur with it.
i will try tonight to update to latest snapshot and see it continues
-
"when the issue happens i renew the ip (or unplug and plug the lan cable of the client) and works for another while"
What could that possible have to do with dns on the pfsense box??
If it was pfsense having the issue you could plug and unplug a client from now until doomsday and it would have no effect.
Like saying my car wont start unless the porch light is on..
Lets see some actual valid tests.. Do a nslookup or dig to your pfsense box.
example
C:\Windows\System32>dig pfsense.local.lan
; <<>> DiG 9.7.2-P3 <<>> pfsense.local.lan
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49875
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0;; QUESTION SECTION:
;pfsense.local.lan. IN A;; ANSWER SECTION:
pfsense.local.lan. 3600 IN A 192.168.1.253;; Query time: 4 msec
;; SERVER: 192.168.1.253#53(192.168.1.253)
;; WHEN: Sun Jan 30 10:13:23 2011
;; MSG SIZE rcvd: 51C:\Windows\System32>nslookup
Default Server: pfsense.local.lan
Address: 192.168.1.253pfsense.local.lan
Server: pfsense.local.lan
Address: 192.168.1.253Name: pfsense.local.lan
Address: 192.168.1.253What do these tests show when your saying its failing?? Lets see the output of your ipconfig /all when this happens.
Is the lease expired?? Ok now lets see this error happen.. You ipconfig /release /renew and now your dig/nslookup pfsense.local.lan works?
edit: if dig to name is not work, ie your having problem with resolving - lets see the results with pointing direct to IP.
dig @192.168.1.253
nslookupserver 192.168.1.253
Would be mine – use the IP of your pfsense box.
-
ip address conflict?
