Home
%3CLINGO-SUB%20id%3D%22lingo-sub-1045241%22%20slang%3D%22en-US%22%3EConfiguring%20the%20new%20ILB%20ASE%20v2's%20DNS%20records%20on%20Azure%20Private%20DNS.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1045241%22%20slang%3D%22en-US%22%3E%3CP%3EWith%20the%20release%20of%20the%20new%20ILB%20ASE%20v2%20(appservicenvironment.net)%2C%20it's%20a%20common%20ask%20from%20customers%20to%20help%20them%20configure%20an%20Azure%20Private%20DNS%20to%20manage%20the%20ILB%20ASE's%20DNS%20records.%3C%2FP%3E%0A%3CP%3EI'll%20describe%20step-by-step%20how%20to%20create%20each%20record%20listed%20under%20the%26nbsp%3B%3CA%20title%3D%22Create%20ILB%20ASE%22%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fapp-service%2Fenvironment%2Fcreate-ilb-ase%23dns-configuration%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EDNS%20configuration%3C%2FA%3E%20section%20of%20the%20%3CA%20title%3D%22Create%20and%20use%20an%20Internal%20Load%20Balancer%20App%20Service%20Environment%22%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fapp-service%2Fenvironment%2Fcreate-ilb-ase%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3ECreate%20and%20use%20an%20Internal%20Load%20Balancer%20App%20Service%20Environment%3C%2FA%3E%26nbsp%3Bdocument.%3C%2FP%3E%0A%3CP%3EIt's%20important%20to%20note%20that%20records%20on%20Azure%20Private%20DNS%20Zones%20will%20only%20be%20resolvable%20by%20resources%20inside%20the%20VNet(s)%20to%20which%20the%20Zone%20has%20been%20linked%20to.%20Consider%20this%20if%20you%20have%20resources%20that%20cannot%20use%20this%20Azure%20Private%20DNS%20Zone%20(like%20on-prem%20resources).%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId--1439522537%22%20id%3D%22toc-hId--1439522537%22%20id%3D%22toc-hId--1439522537%22%3E%3CSPAN%3ECreate%20a%20zone%20for%26nbsp%3B%3C%2FSPAN%3E%3CEM%3E%3CASE%20name%3D%22%22%3E.appserviceenvironment.net%3C%2FASE%3E%3C%2FEM%3E%3C%2FH2%3E%0A%3CP%20style%3D%22padding-left%3A%2030px%3B%22%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2030px%3B%22%3E1.%20In%20the%20%3CA%20title%3D%22Azure%20Portal%22%20href%3D%22https%3A%2F%2Fportal.azure.com%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EAzure%20Portal%3C%2FA%3E%2C%20click%20in%20the%3CSPAN%3E%26nbsp%3Bportal%20search%20bar%2C%20type%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3Eprivate%20dns%20zones%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3Bin%20the%20search%20text%20box%20and%20press%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3EEnter%3C%2FSTRONG%3E%3CSPAN%3E.%26nbsp%3B%3C%2FSPAN%3EThis%20will%20start%20the%20%3CSTRONG%3ECreate%20Private%20DNS%20zone%3C%2FSTRONG%3E%20experience.%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2060px%3B%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F159900iA720252610582088%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22clipboard_image_0.png%22%20title%3D%22clipboard_image_0.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2030px%3B%22%3E2.%20Select%20the%20%3CSTRONG%3ESubscription%3C%2FSTRONG%3E%20that%20contains%20your%20ILB%20ASE's%20VNet.%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2030px%3B%22%3E3.%20Create%20or%20select%20an%20existing%20%3CSTRONG%3EResource%20Group.%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2030px%3B%22%3E4.%20In%26nbsp%3B%3CSTRONG%3EName%26nbsp%3B%3C%2FSTRONG%3Eunder%26nbsp%3B%3CSTRONG%3EInstance%20details%26nbsp%3B%3C%2FSTRONG%3Etype%20%3CEM%3E%3CASE%20name%3D%22%22%3E.appserviceenvironment.net%3C%2FASE%3E%3C%2FEM%3E%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2030px%3B%22%3E5.%20In%20%3CSTRONG%3EResource%20group%20location%3C%2FSTRONG%3E%20select%20the%20same%20location%20as%20your%20ILB%20ASE's%20VNet.%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2030px%3B%22%3E6.%20Click%20%3CSTRONG%3EReview%20%2B%20create%3C%2FSTRONG%3E%20and%20then%26nbsp%3B%3CSTRONG%3ECreate%3C%2FSTRONG%3E.%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2030px%3B%22%3E7.%20Once%20the%20deployment%20finishes%20click%20in%20%3CSTRONG%3EGo%20to%20resource%3C%2FSTRONG%3E.%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2030px%3B%22%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-1047990296%22%20id%3D%22toc-hId-1047990296%22%20id%3D%22toc-hId-1047990296%22%3E%3CSPAN%3ECreate%20an%20A%20record%20in%20that%20zone%20that%20points%20*%20to%20the%20ILB%20IP%20address%3C%2FSPAN%3E%3C%2FH2%3E%0A%3CP%20style%3D%22padding-left%3A%2030px%3B%22%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2030px%3B%22%3E8.%20In%20your%20Azure%20Private%20DNS%20Zone%2C%20click%20in%20%3CSTRONG%3E%2BRecord%20set%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2060px%3B%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F159901iAB63FB3BFADDBB3B%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22clipboard_image_0.png%22%20title%3D%22clipboard_image_0.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2030px%3B%22%3E9.%20Fill%20out%20the%20following%20information%20and%20then%20click%20%3CSTRONG%3EOK%3C%2FSTRONG%3E%3A%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2060px%3B%22%3E%3CSTRONG%3EName%3A%3C%2FSTRONG%3E%26nbsp%3B*%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2060px%3B%22%3E%3CSTRONG%3EType%3A%3C%2FSTRONG%3E%26nbsp%3BA%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2060px%3B%22%3E%3CSTRONG%3EIP%20address%3A%26nbsp%3B%3C%2FSTRONG%3E%3CEM%3E%3CILB%20ip%3D%22%22%20address%3D%22%22%3E%3CBR%20%2F%3E%3C%2FILB%3E%3C%2FEM%3ENote%3A%20You%20can%20find%20this%20under%20your%20ILB%20ASE's%20IP%20address%20blade%2C%20listed%20as%26nbsp%3B%3CSTRONG%3EInternal%20Load%20Balancer%20IP%20address%3C%2FSTRONG%3E.%20In%20my%20case%20my%20ILB%20ASE's%20IP%20is%20172.20.0.11%3A%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2060px%3B%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F159903iCBC1D55EFCA61D43%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22clipboard_image_1.png%22%20title%3D%22clipboard_image_1.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2060px%3B%22%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId--759464167%22%20id%3D%22toc-hId--759464167%22%20id%3D%22toc-hId--759464167%22%3E%3CSPAN%3ECreate%20an%20A%20record%20in%20that%20zone%20that%20points%20%40%20to%20the%20ILB%20IP%20address%3C%2FSPAN%3E%3C%2FH2%3E%0A%3CP%20style%3D%22padding-left%3A%2030px%3B%22%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2030px%3B%22%3E10.%20Click%20on%20%3CSTRONG%3E%2B%20Record%20set%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2030px%3B%22%3E11.%26nbsp%3BFill%20out%20the%20following%20information%20and%20then%20click%20%3CSTRONG%3EOK%3C%2FSTRONG%3E%3A%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2060px%3B%22%3E%3CSTRONG%3EName%3A%26nbsp%3B%3C%2FSTRONG%3E%3CEM%3E%40%3C%2FEM%3E%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2060px%3B%22%3E%3CSTRONG%3EType%3A%3C%2FSTRONG%3E%20A%3CBR%20%2F%3E%3CSTRONG%3EIP%20address%3A%26nbsp%3B%3C%2FSTRONG%3E%3CEM%3E%3CILB%20ip%3D%22%22%20address%3D%22%22%3E%3CBR%20%2F%3E%3C%2FILB%3E%3C%2FEM%3EThis%20is%20the%20same%20IP%20address%20used%20in%20Step%209.%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2060px%3B%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F159907iAB0C72EB0D9345AB%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22clipboard_image_0.png%22%20title%3D%22clipboard_image_0.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2060px%3B%22%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-1728048666%22%20id%3D%22toc-hId-1728048666%22%20id%3D%22toc-hId-1728048666%22%3E%3CSPAN%3ECreate%20a%20zone%20in%20%3C%2FSPAN%3E%3CEM%3E%3CASE%20name%3D%22%22%3E.appserviceenvironment.net%3C%2FASE%3E%3C%2FEM%3E%3CSPAN%3E%20named%20scm%3C%2FSPAN%3E%3C%2FH2%3E%0A%3CP%20style%3D%22padding-left%3A%2060px%3B%22%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2030px%3B%22%3E12.%20The%20article%20says%20%22create%20a%20zone%20in%22%20which%20will%20correspond%20to%20a%20subdomain%2C%20but%20since%20Azure%20Private%20DNS%20Zone%20doesn't%20seem%20to%20have%20an%20option%20to%20create%20a%20subdomain%20this%20means%20either%20creating%20a%20separate%20zone%20called%26nbsp%3B%3CSTRONG%3E%3CEM%3Escm.%3CASE%20name%3D%22%22%3E.appserviceenvironment.net%26nbsp%3B%3C%2FASE%3E%3C%2FEM%3E%3C%2FSTRONG%3E(more%20expensive)%20or%20simply%20creating%20a%20wildcard%20record%20for%20%3CSTRONG%3E%3CEM%3E*.scm%3C%2FEM%3E.%3C%2FSTRONG%3E%26nbsp%3BWe'll%20explain%20how%20to%20do%20the%20latter.%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2030px%3B%22%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId--79405797%22%20id%3D%22toc-hId--79405797%22%20id%3D%22toc-hId--79405797%22%3E%3CSPAN%3ECreate%20an%20A%20record%20in%20the%20scm%20zone%20that%20points%20*%20to%20the%20ILB%20IP%20address.%3C%2FSPAN%3E%3C%2FH2%3E%0A%3CP%20style%3D%22padding-left%3A%2030px%3B%22%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2030px%3B%22%3E13.%20In%20your%20Azure%20Private%20DNS%20Zone%2C%20click%20in%20%3CSTRONG%3E%2BRecord%20set%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2060px%3B%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F159901iAB63FB3BFADDBB3B%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22clipboard_image_0.png%22%20title%3D%22clipboard_image_0.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2030px%3B%22%3E14.%20Fill%20out%20the%20following%20information%20and%20then%20click%20%3CSTRONG%3EOK%3C%2FSTRONG%3E%3A%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2060px%3B%22%3E%3CSTRONG%3EName%3A%3C%2FSTRONG%3E%26nbsp%3B*.scm%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2060px%3B%22%3E%3CSTRONG%3EType%3A%3C%2FSTRONG%3E%26nbsp%3BA%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2060px%3B%22%3E%3CSTRONG%3EIP%20address%3A%26nbsp%3B%3C%2FSTRONG%3E%3CEM%3E%3CILB%20ip%3D%22%22%20address%3D%22%22%3E%3CBR%20%2F%3E%3C%2FILB%3E%3C%2FEM%3EThis%20is%20the%20same%20IP%20address%20as%20in%20Step%209.%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2060px%3B%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F160056i24D988E5892275BB%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22clipboard_image_0.png%22%20title%3D%22clipboard_image_0.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2060px%3B%22%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20style%3D%22padding-left%3A%2030px%3B%22%20id%3D%22toc-hId--1886860260%22%20id%3D%22toc-hId--1886860260%22%20id%3D%22toc-hId--1886860260%22%3EAssign%20the%20Azure%20Private%20DNS%20zone%20to%20the%20ILB%20ASE's%20VNet%3C%2FH2%3E%0A%3CP%20style%3D%22padding-left%3A%2030px%3B%22%3E15.%20Click%20in%20Virtual%20network%20links%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2060px%3B%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F160057i0D77E30DE7B7DCD2%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22clipboard_image_0.png%22%20title%3D%22clipboard_image_0.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2030px%3B%22%3E16.%20Click%20%3CSTRONG%3EAdd%2B%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2030px%3B%22%3E17.%20Fill%20out%20the%20following%20information%20and%20then%20click%20%3CSTRONG%3EOk%3C%2FSTRONG%3E%3A%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2060px%3B%22%3E%3CSTRONG%3ELink%20name%3A%26nbsp%3B%3C%2FSTRONG%3E%3CANY%20name%3D%22%22%3E%20There's%20no%20requirement%20as%20to%20what%20name%20to%20use%20but%20I%20recommend%20using%20a%20descriptive%20name%20something%20like%20%3CVNET%20name%3D%22%22%3E-PrivateDNS-Link%3C%2FVNET%3E%3C%2FANY%3E%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2060px%3B%22%3E%3CSTRONG%3ESubscription%3A%26nbsp%3B%3C%2FSTRONG%3ESelect%20the%20subscription%20that%20contains%20the%20ASE's%20VNet%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2060px%3B%22%3E%3CSTRONG%3EVirtual%20network%3A%20%3C%2FSTRONG%3ESelect%20the%26nbsp%3BASE's%20VNet%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2060px%3B%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F161181i1F685464EB84F723%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22clipboard_image_0.png%22%20title%3D%22clipboard_image_0.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2030px%3B%22%3E18.%20After%20it%20finishes%20adding%20it%2C%20you%20should%20be%20able%20to%20see%20the%20link%20under%20Virtual%20network%20links.%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2060px%3B%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F161183iCE40EAAC22174873%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22clipboard_image_1.png%22%20title%3D%22clipboard_image_1.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2030px%3B%22%3ENow%20Web%20Apps%20running%20on%20this%20ASE%20or%20Azure%20VMs%20on%20this%20VNet%2C%20should%20be%20able%20to%20resolve%20any%20Web%20App%20name%20or%20kudu%20console%20(SCM)%20created%20on%20this%20ASE.%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2030px%3B%22%3EThe%20ILB%20ASE's%20IP%20address%20won't%20change%20unless%20the%20ASE%20is%20suspended%2C%20so%20you%20shouldn't%20need%20to%20modify%20these%20records%20in%20the%20future.%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2030px%3B%22%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1045241%22%20slang%3D%22en-US%22%3E%3CP%3EWith%20the%20release%20of%20the%20new%20ILB%20ASE%20v2%20(appservicenvironment.net)%2C%20it's%20a%20common%20ask%20from%20customers%20to%20help%20them%20configure%20an%20Azure%20Private%20DNS%20to%20manage%20the%20ILB%20ASE's%20DNS%20records.%3C%2FP%3E%0A%3CP%3EI'll%20describe%20step-by-step%20how%20to%20create%20each%20record%20listed%20under%20the%26nbsp%3B%3CA%20title%3D%22Create%20ILB%20ASE%22%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fapp-service%2Fenvironment%2Fcreate-ilb-ase%23dns-configuration%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EDNS%20configuration%3C%2FA%3E%20section%20of%20the%20%3CA%20title%3D%22Create%20and%20use%20an%20Internal%20Load%20Balancer%20App%20Service%20Environment%22%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fapp-service%2Fenvironment%2Fcreate-ilb-ase%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3ECreate%20and%20use%20an%20Internal%20Load%20Balancer%20App%20Service%20Environment%3C%2FA%3E%26nbsp%3Bdocument.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1109443%22%20slang%3D%22en-US%22%3ERe%3A%20Configuring%20the%20new%20ILB%20ASE%20v2's%20DNS%20records%20on%20Azure%20Private%20DNS.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1109443%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%20We%20are%20using%20the%20on-premise%20DNS%20servers%20for%20name%20resolution%20in%20internal%20ASE.%20I%20have%20created%20a%20zone%20in%20the%20DNS%20server%20(Windows%20server%202019%20core)%20for%20our%20ILB%20ASE%20with%20name%20%3CASENAME%3E.appserviceenvironment.net.%20*%20record%20was%20created%20for%20app%20services%20and%20name%20resolution%20for%20app%20services%20are%20working.%3C%2FASENAME%3E%3C%2FP%3E%3CP%3EAlso%20created%20a%20*.scm%20record%20for%20the%20kudu.%20But%20facing%20issues%20for%20kudu%20url%20access.%20App%20service%20is%20giving%20kudu%20url%20name%20resolution%20issues%20while%20application%20deployment.%3C%2FP%3E%3CP%3EI%20was%20unable%20to%20create%26nbsp%3B%40%20record%20in%20the%20newly%20created%20zone.%20The%20error%20message%20is%20%22The%20host%20record%20%40.%3CASENAME%3E.appserviceenvironment.net.%22%20cannot%20be%20created.%20The%20name%20is%20invalid.%20Please%20help%20to%20get%20this%20resolved.%3C%2FASENAME%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Microsoft

With the release of the new ILB ASE v2 (appservicenvironment.net), it's a common ask from customers to help them configure an Azure Private DNS to manage the ILB ASE's DNS records.

I'll describe step-by-step how to create each record listed under the DNS configuration section of the Create and use an Internal Load Balancer App Service Environment document.

It's important to note that records on Azure Private DNS Zones will only be resolvable by resources inside the VNet(s) to which the Zone has been linked to. Consider this if you have resources that cannot use this Azure Private DNS Zone (like on-prem resources).

Create a zone for <ASE name>.appserviceenvironment.net

 

1. In the Azure Portal, click in the portal search bar, type private dns zones in the search text box and press EnterThis will start the Create Private DNS zone experience.

clipboard_image_0.png

2. Select the Subscription that contains your ILB ASE's VNet.

3. Create or select an existing Resource Group.

4. In Name under Instance details type <ASE name>.appserviceenvironment.net

5. In Resource group location select the same location as your ILB ASE's VNet.

6. Click Review + create and then Create.

7. Once the deployment finishes click in Go to resource.

 

Create an A record in that zone that points * to the ILB IP address

 

8. In your Azure Private DNS Zone, click in +Record set

clipboard_image_0.png

9. Fill out the following information and then click OK:

Name: *

Type: A

IP address: <ILB IP address>
Note: You can find this under your ILB ASE's IP address blade, listed as Internal Load Balancer IP address. In my case my ILB ASE's IP is 172.20.0.11:

clipboard_image_1.png

 

Create an A record in that zone that points @ to the ILB IP address

 

10. Click on + Record set

11. Fill out the following information and then click OK:

Name: @

Type: A
IP address: <ILB IP address>
This is the same IP address used in Step 9.

clipboard_image_0.png

 

Create a zone in <ASE name>.appserviceenvironment.net named scm

 

12. The article says "create a zone in" which will correspond to a subdomain, but since Azure Private DNS Zone doesn't seem to have an option to create a subdomain this means either creating a separate zone called scm.<ASE name>.appserviceenvironment.net (more expensive) or simply creating a wildcard record for *.scm. We'll explain how to do the latter.

 

Create an A record in the scm zone that points * to the ILB IP address.

 

13. In your Azure Private DNS Zone, click in +Record set

clipboard_image_0.png

14. Fill out the following information and then click OK:

Name: *.scm

Type: A

IP address: <ILB IP address>
This is the same IP address as in Step 9.

clipboard_image_0.png

 

Assign the Azure Private DNS zone to the ILB ASE's VNet

15. Click in Virtual network links

clipboard_image_0.png

16. Click Add+

17. Fill out the following information and then click Ok:

Link name: <Any name> There's no requirement as to what name to use but I recommend using a descriptive name something like <VNet name>-PrivateDNS-Link

Subscription: Select the subscription that contains the ASE's VNet

Virtual network: Select the ASE's VNet

clipboard_image_0.png

18. After it finishes adding it, you should be able to see the link under Virtual network links.

clipboard_image_1.png

Now Web Apps running on this ASE or Azure VMs on this VNet, should be able to resolve any Web App name or kudu console (SCM) created on this ASE.

The ILB ASE's IP address won't change unless the ASE is suspended, so you shouldn't need to modify these records in the future.

 

1 Comment
Occasional Visitor

Hi, We are using the on-premise DNS servers for name resolution in internal ASE. I have created a zone in the DNS server (Windows server 2019 core) for our ILB ASE with name <ASEname>.appserviceenvironment.net. * record was created for app services and name resolution for app services are working.

Also created a *.scm record for the kudu. But facing issues for kudu url access. App service is giving kudu url name resolution issues while application deployment.

I was unable to create @ record in the newly created zone. The error message is "The host record @.<asename>.appserviceenvironment.net." cannot be created. The name is invalid. Please help to get this resolved.