@Cry:

In BIND you have to terminate any name with a dot to avoid it having $ORIGIN appended.  I would treat all other DNS servers as behaving the same unless their documentation says otherwise.

So I've added a dot to any name, now it's look like this:
Record Name                Record Type   rDNS       Record Data                TTL
mydomain.com.                    SOA                pfsense.mydomain.com.
test.mydomain.com.             A            on      192.168.1.1
cnametest.mydomain.com.    CNAME              test.mydomain.com.

But it still not working, if I'm trying to ping cnametest.mydomain.com Im still getting "could not find host …Please check the name and try again"

Also when I'm doing an nslookup for the cname Im getting something weird:

nslookup cnametest.mydomain.com
Server:  pfsense.mydomain.com
Address:  192.168.1.1

Name:    cnametest.mydomain.com
Served by:

pfsense.mydomain.com
         192.168.1.1
         mydomain.com

Served by?? So it found something but it's able to resolved it correctly?

Thank you for your time

It's been a while, sorry.

This could be interesting for you:  http://forum.pfsense.org/index.php/topic,22890.0/topicseen.html
especially the NIC with built in NWAY switch.
Until I remembered that you were talking about an ALIX install…

Hi guys,

thx very much for this excellent explanation.

Well done.

hy,

nickolas

You set it up under the DHCP server options:

http://doc.pfsense.org/index.php/DHCP_Server

I saw exactly that problem on the Telewest (now VirginMedia) network many years ago and had some chats with their back end technical staff at the time (I have a background in networking and took great care to email in a ticket that would demonstrate the problem, that I knew what I was talking about and that I wanted to help them fix their system).

The problem was with the DHCP servers at the ISP and wasn't something that could be fixed at the customer end.  They did fix it, but obviously the problem is back.  There isn't anything you can do unfortunately except log a ticket with them and get frustrated over explaining the problem (since most of their customer base won't have noticed).

I'd be more interested in the DHCP setup you have in place.  You don't have just one scope serving out all 1500 addresses do you?  Everything I've always heard (and what Cisco teaches) is to only have 255 clients per scope(VLAN).  It helps with ARP requests on switches and I think it could improve your pfSense DHCP page loading issue.

@particleman:

The purpose of listing two dns is just in case one fails , correct?

I think I have read that a DNS client asks all the servers concurrently (presumably to get the fastest response, particularly if a server is not contactable).

Try again in about 5-10 minutes. I just checked in a fix.

Doh! Thank you! Works as expected now.

Ok I think I understand now.  I am currently using my existing Bind server and having it handle my domain, and then forward to pfSense for internet requests.

Thanks guys, I will try the 2.0 beta.

Kind regards,

Jozef00

Anyone?

XP's repair option does renew the IP address, but I'm not sure it does a release first.

Vista/7 go even farther in their 'Diagnose' option, they disable/enable the whole adapter as part of the routine.

H