• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

Error when setting DNS Servers

Scheduled Pinned Locked Moved IPv6
10 Posts 5 Posters 6.4k Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A
    alexis.olivier
    last edited by Sep 1, 2011, 1:18 PM

    Hello,

    I got this error when trying to setup my DNS Servers in System > General Setup :

    
    The gateway specified for DNS server '10.130.0.142' is not from the same Address Family as gateway ''.
    The gateway specified for DNS server '10.14.32.30' is not from the same Address Family as gateway ''.
    The gateway specified for DNS server '' is not from the same Address Family as gateway ''.
    The gateway specified for DNS server '' is not from the same Address Family as gateway ''.
    
    

    My version :
    2.1-DEVELOPMENT  (amd64)
    built on Wed Aug 31 17:02:22 EDT 2011

    Thank you !

    1 Reply Last reply Reply Quote 0
    • D
      databeestje
      last edited by Sep 3, 2011, 10:29 AM

      Will investigate.

      1 Reply Last reply Reply Quote 0
      • A
        alexis.olivier
        last edited by Sep 8, 2011, 9:23 AM Sep 8, 2011, 7:39 AM

        Do you you have news on this problem ?

        I can't update my general configuration unless i patch the code to remove the DNS checks.

        1 Reply Last reply Reply Quote 0
        • D
          databeestje
          last edited by Sep 8, 2011, 7:50 AM

          Have not gotten round to it.

          1 Reply Last reply Reply Quote 0
          • D
            databeestje
            last edited by Sep 8, 2011, 7:07 PM

            Can not replicate anymore, does this still fail for you.

            1 Reply Last reply Reply Quote 0
            • _
              __nicolas__
              last edited by Nov 10, 2011, 4:22 PM

              Hello,

              Got the same problem.

              My build: 2.1-DEVELOPMENT-pfSense (i386), the lastest available until now (that's the 2011-Oct-22 01:44:57 build on iso image)

              Perhaps some more informations:

              I configured 3 NIC:
              em0 (LAN) ipv4 (192.168.x.x) and IPv6 (2001:db8:0:f101::1079:1/64)
              em1_vlan15 (Internet area) IPv6 only (2001:db8:0:0::4/64)
              em1_vlan16 (Other network) IPV6 only (where DNS are located) (2001:db8:0:1::1/64)

              DNS are : 2001:db8:0:1::53:1 and 2001:db8:0:1::53:2

              I tried to setup another DNS (let's say 8.8.4.4), but it is the same problem.

              I have no default gw (v4 and/or v6) set.

              If I set a V4 gw and a V4 IP on WAN (em1_lan15) the update can be done.

              I hope that helps ;-)

              Regards,
              nicolas.

              PS: IPv6 IP are in documentation Area … do not use them asis ;-)

              Nicolas

              1 Reply Last reply Reply Quote 0
              • K
                Kekskrümel
                last edited by Nov 16, 2011, 11:16 AM

                Hi,

                same here.

                Added without the setup wizard on WAN and LAN Interface an IPv4 Adress and tryed to add an IPv4 DNS Server. Same error as alexis.olivier.
                Same with IPv6 Adress on the Interfaces and DNS Server.

                Greetings

                1 Reply Last reply Reply Quote 0
                • J
                  johnpoz LAYER 8 Global Moderator
                  last edited by Nov 16, 2011, 12:38 PM

                  I just went in and changed mine to an ipv6 and ipv4 google from the normal ones I have set 127.0.0.1 and 4.2.2.2

                  No issues - see attached

                  2.1-DEVELOPMENT (i386)
                  built on Fri Oct 21 12:51:56 EDT 2011
                  FreeBSD 8.1-RELEASE-p6

                  gitsync as of last night

                  noissuedns.jpg
                  noissuedns.jpg_thumb

                  An intelligent man is sometimes forced to be drunk to spend time with his fools
                  If you get confused: Listen to the Music Play
                  Please don't Chat/PM me for help, unless mod related
                  SG-4860 24.11 | Lab VMs 2.7.2, 24.11

                  1 Reply Last reply Reply Quote 0
                  • K
                    Kekskrümel
                    last edited by Nov 17, 2011, 1:33 PM

                    Using

                    http://files.pfsense.org/jimp/ipv6/

                    pfSense-2.1-DEVELOPMENT-amd64.iso.gz 2011-Oct-22 02:32:39

                    Greetings

                    1 Reply Last reply Reply Quote 0
                    • K
                      Kekskrümel
                      last edited by Nov 28, 2011, 5:31 PM

                      Same error with the new build.

                      If I edit the restore file with 2 ipv6 dns server, both are configured in pfsense after the restore.

                      But Package and Update management doesn't work.

                      Unable to communicate with www.pfsense.com. Please verify DNS and interface configuration, and that pfSense has functional Internet connectivity.

                      DNS Lookup with the both IPv6 DNS Server works fine.

                      Diagnostic -> DNS Lookup

                      pfsense.com = 69.64.6.21

                      2a01:4f8:120:5121:6::53 6 msec
                      2001:4d88:1ffc:409:1::53 8 msec

                      Any Idears ?

                      Thx

                      Greetings

                      1 Reply Last reply Reply Quote 0
                      • First post
                        Last post
                      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                        This community forum collects and processes your personal information.
                        consent.not_received