DNS problem with 0.95.8

thinair

I have the same issue.

In the resolv.conf file and nameserver file I get the same thing, just with my ISP's DNS server instead.

Below is the GUI, looks sorta weird, the ISP DNS servers cell is missing.

pfsenseWAN.gif_thumb

sullrich

Okay, thats cosmetic.

I'll fix now.

sullrich

I can't duplicate the issue with stock DHCP. I guess everyone is running PPPoE? I see thinair's screenshot which supports this hunch.

Please modify /etc/rc.newwanip and insert:

/* regenerate DNS servers / resolv.conf */
system_resolvconf_generate();

Right before:

/* signal filter reload */
touch("/tmp/filter_dirty");

Does it fix it?

Emab

I've chnaged rc.newwanip.

Now i've the "ISP DNS servers" filed in GUI, but it's blank. And the DNS is still not running…

sullrich

@Emab:

I've chnaged rc.newwanip.

Now i've the "ISP DNS servers" filed in GUI, but it's blank. And the DNS is still not running…

What does /var/etc/resolv.conf show now?

Please make a screenshot of what you mean as blank.

thinair

not for me….

still the same as it was.

sullrich

update_file.sh /etc/inc/pfsense-utils.inc

And please try again.

thinair

I did that and rebooted, still not resolved.

sullrich

Okay, I'm still waking up, but I think that it should be okay now.

update_file.sh /etc/inc/pfsense-utils.inc

And reboot again.

BUMP! Please test this ASAP, I'm about out of time for the day and need to get a new version out the door if this fixes your issue!

Emab

Still not running.

Now I get "Fatal error: Call to a member function on a non-object in /etc/inc/pfsense-utils.inc on line 1118" going in the Firmware menu (/system_firmware_check.php).

In the GUI, in Interface, now i can read the DNS. This is the HTML:

ISP DNS servers

		85.37.17.13

(I noted the two "
". I think it's only comestic).

/var/etc/nameserver.conf is not found.

# cat /var/etc/resolv.conf
domain local

Tell me if you need anything else.

Best.
Emanuele

sullrich

That is because we mixed head with RELENG_1. Try this from a shell:

fetch -o /etc/inc/pfsense-utils.inc "http://cvs.pfsense.com/cgi-bin/cvsweb.cgi/~checkout~/pfSense/etc/inc/pfsense-utils.inc?rev=1.316.2.23;content-type=text%2Fplain;only_with_tag=RELENG_1"

thinair

@sullrich:

Okay, I'm still waking up, but I think that it should be okay now.

update_file.sh /etc/inc/pfsense-utils.inc

And reboot again.

BUMP! Please test this ASAP, I'm about out of time for the day and need to get a new version out the door if this fixes your issue!

still the same

sullrich

I'm at a loss, because Emab says the interfaces now show in interfaces status.

What i've done REALLY should have fixed it.

thinair

@sullrich:

That is because we mixed head with RELENG_1. Try this from a shell:

fetch -o /etc/inc/pfsense-utils.inc "http://cvs.pfsense.com/cgi-bin/cvsweb.cgi/~checkout~/pfSense/etc/inc/pfsense-utils.inc?rev=1.316.2.23;content-type=text%2Fplain;only_with_tag=RELENG_1"

still the same :(

Emab

I try with

fetch -o /etc/inc/pfsense-utils.inc "http://cvs.pfsense.com/cgi-bin/cvsweb.cgi/~checkout~/pfSense/etc/inc/pfsense-utils.inc?rev=1.316.2.23;content-type=text%2Fplain;only_with_tag=RELENG_1"

But still not running…

sullrich

@Emab:

I try with

fetch -o /etc/inc/pfsense-utils.inc "http://cvs.pfsense.com/cgi-bin/cvsweb.cgi/~checkout~/pfSense/etc/inc/pfsense-utils.inc?rev=1.316.2.23;content-type=text%2Fplain;only_with_tag=RELENG_1"

But still not running…

Sorry but I am out of options/fixes then.

sullrich

Wait, found some more stuff…

sullrich

Okay, run this from a shell:

/etc/rc.conf_mount_rw
fetch -o /etc/inc/system.inc "http://cvs.pfsense.com/cgi-bin/cvsweb.cgi/~checkout~/pfSense/etc/inc/system.inc?rev=1.79.2.12;content-type=text%2Fplain;only_with_tag=RELENG_1"

thinair

I get this:
fetch: http://cvs.pfsense.com/cgi-bin/cvsweb.cgi/~checkout~/pfSense/etc/inc/system.inc?rev=1.79.2.12;content-type=text%2Fplain;only_with_tag=RELENG_1: No address record

In fact I've always gotten that no address record message with every fetch entered here.

Anyway, still didn't work. I appreciate the effort you're putting into this though. I guess it is a PPPoE thing?

sullrich

Wait for the next update then.