SRX

Hi there

Is it possible to have a Connection-specific DNS Suffix appled when connecting to Dynamic VPN ? This is the current configuration but when it connects the DNS Suffix is not populated.

 pool 192.168.1.0/24 {
                address-range low 192.168.1.2 high 192.168.1.254;
                domain-search {
                    domain.local;
                }
                router {
                    192.168.1.1;
                }
                propagate-settings ge-0/0/0.0;
            }

Our configuration is

Juniper SRX 240

JUNOS Software Release [12.1R4.7]

Pulse Client 5.0

VPN: Inbuild dynamic VPN

Regards

set system services dhcp pool 192.168.1.0/24 name-server 192.168.1.10

where name-server IP is the address of the DNS server that can resolve planit.local

I think that should work No test bed for it at the moment.

Sorry to bump an old thread but still having the same issue even after adding the name-server. Apoligies to the original post as some network details have changed. Once you connect with Pulse 5 (SRX, Dynamic VPN) the DNS suffix is empty (see cmd) 

I can ping server1.mydomain.local but not server1 because DNS suffix is missing. 10.2.20.6 is the DNS.

Config

address-assignment {
        pool dyn-vpn-address-pool {
            family inet {
                network 10.1.20.0/24;
                dhcp-attributes {
                    domain-name mydomain.local;
                    name-server {
                        10.2.20.6;
                    }
                }
                xauth-attributes {
                    primary-dns 10.2.20.6/32;
                }
            }
        }
    }

 Adapter (cmd)

I believe this is know issue.

http://kb.juniper.net/InfoCenter/index?page=content&id=KB26257

Thanks,

Suraj

Please Mark My Solution Accepted if it Helped, Kudos are Appreciated too

Hi rsuraj

Thanks and marked as solution. Do you know if any of the 12.1X releases have fixed this or where I go to find out if the attribute will ever be introduced?

Regards

As of now this is a limitation. To get the roadmap for this feature I would suggest contacting Juniper Sales/Accounts team.

Thanks,

Suraj

Please Mark My Solution Accepted if it Helped, Kudos are Appreciated too

Has this been resolved?