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

Wpad setup problem

Scheduled Pinned Locked Moved Cache/Proxy
4 Posts 2 Posters 1.0k 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.
  • T
    techbee
    last edited by Jun 21, 2017, 4:36 AM Jun 21, 2017, 4:27 AM

    In pursue to setup https web filtering  using wpad,  I am configuring the DNS resolver with
    hostname=wpad
    domain=localdomain.local
    ip=192.168.1.1

    my pfsense local ip address is 192.168.1.1 and I am using http protocol on my general setup.

    When I nslookup wpad 127.0.0.1 from my pfsense box, I get:

    Server:        127.0.0.1
    Address:        127.0.0.1#53

    Name:  wpad.localdomain.local
    Address: 192.168.1.1

    When I nslookup wpad 192.168.1.1 from my pfsense box, I get:

    Server:        192.168.1.1
    Address:      192.168.1.1#53

    ** server can't find wpad: NXDOMAIN

    But when I nslookup wpad 192.168.1.1 from my lan compputer, I get:

    Server:  pfSense.localdomain.local
    Address:  192.168.1.1

    *** pfSense.localdomain.local can't find wpad: Non-existent domain

    But when I nslookup wpad.localdomain.local 192.168.1.1 from my lan compputer, I get:

    Server:  pfSense.localdomain.local
    Address:  192.168.1.1

    Name:    wpad.localdomain.local
    Address:  192.168.1.1

    What do I miss here ?

    1 Reply Last reply Reply Quote 0
    • K
      KOM
      last edited by Jun 21, 2017, 2:06 PM

      What do I miss here ?

      Is your client a member of localdomain.local?  Is localdomain.local the default domain when doing lookups?  Your DNS only responds to lookup requests for wpad.localdomain.local not wpad by itself, so your client would have to know to add the domain.

      1 Reply Last reply Reply Quote 0
      • T
        techbee
        last edited by Jun 21, 2017, 10:50 PM

        yes. the clients dns and gateway are on 192.168.1.1

        1 Reply Last reply Reply Quote 0
        • K
          KOM
          last edited by Jun 22, 2017, 1:19 PM

          That's not what I asked.

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