You can define additional FQDNs somewhere in the GUI. I believe when behind PacketFence DNS, these are automatically resolved to the PF server IP address. However, on your production network, you will need to configure A records on your own DNS servers.
I'm specifically asking for a way define the FQDN that users are automatically redirected to. This seems to be hard-coded to be the FQDN of the PF host itself. On Thu, Jan 24, 2019 at 8:47 AM Murilo Calegari < [email protected]> wrote: > I've got the same question! Is it possible to define multiple portal FQDNs > which PacketFence listens to? > > Em qui, 24 de jan de 2019 às 10:34, Christian McDonald via > PacketFence-users <[email protected]> escreveu: > >> Greetings, >> >> The default FQDN of the captive portal that appears in users browsers is >> simply the FQDN of the PacketFence server. Is there a way change this? >> For example, let's say the FQDN of my PF server is " >> nac01.corp.example.com". How can I instead direct users to a more >> friendly name "registration.corp.example.com"? >> >> Thanks, >> >> -- >> *R. Christian McDonald * >> E: [email protected] >> _______________________________________________ >> PacketFence-users mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/packetfence-users >> > -- *R. Christian McDonald * M: (616) 856-9291 E: [email protected]
_______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
